Hi @dwradcliffe,

Thanks for the contribution! One open question:

Is the python-pymongo package name valid on both CentOS/Ubuntu? If not, can you add a platform-specific block, like this one?

Yep, I saw the same package name on both platforms.

I ran a search for Ubuntu, found it only on certain (recent?) versions:
http://packages.ubuntu.com/search?suite=all&arch=any&searchon=names&keywords=python-pymongo

Whereas on CentOS, it's not in the core, and requires EPEL, where the name differs:
http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/pymongo.html

Unless you have a different resource?

Ok, looks like the package only exists for Ubuntu 12.04 and later. Should I make the package conditional based on the Ubuntu version?

The yum EPEL package is under both names (http://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/python-pymongo.html). Just pushed a fix for that.

@dwradcliffe I've been thinking about this one, and I think I'm going to prefer using a non-distro package, rather an easy_install one.

1. distro packages commonly lag a lot behind the available code, sometimes missing performance and/or security patches
2. There's inconsistency for availability among distros, and adding platform-specific code adds complexity to the cookbook.
3. The yum cookbook recently went into a refactor, and yum::epel isn't there any more, and I'd rather not enforce a particular version of a dependency on users that might already be using a yum cookbook, and thereby break their usage.

Would you consider refactoring for a python package installation?

Thanks!

@miketheman Good points, especially the 3rd one.

Would package "python-setuptools" work cross-platform or is there a better way to ensure easy_install is available?

Seems to work for me on Ubuntu and CentOS. Latest code push includes a test-kitchen suite.

Thanks @dwradcliffe ! Merged in, added some testing. Will go in next release!

Awesome!